home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000128_news@columbia.edu_Thu Aug 10 08:14:23 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA27854
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 10 Aug 1995 11:31:13 -0400
Received: by apakabar.cc.columbia.edu id AA11382
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 10 Aug 1995 11:31:11 -0400
Path: news.columbia.edu!spcuna!solaris.cc.vt.edu!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!howland.reston.ans.net!usenet.ins.cwru.edu!cleveland.Freenet.Edu!cn125
From: cn125@cleveland.freenet.edu (Jerry L. Brod)
Newsgroups: comp.protocols.kermit.misc
Subject: MS KERMIT, telnet, and WFW
Date: 10 Aug 1995 08:14:23 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
Lines: 21
Message-Id: <40cf50$9p6@usenet.INS.CWRU.Edu>
Nntp-Posting-Host: kanga.ins.cwru.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
I'm trying to use MS-DOS Kermit to make telnet connections
from Microsoft Windows for Workgroups 3.11. I have examined
the MSKWFW.DOC file and found that our situation seems to be
covered by text #3, situation 3: WFW uses NDIS version 3 handler
and its own TCP/IP stack. The text states:
An alternative for those owning the Microsoft TCP/IP
protocol stack is to run Kermit over that stack. The
Kermit command to do this is SET PORT 3COM(BAPI), and
that talks to WFW protected-mode agent VBAPI.386.
Host selection occurs while talking to the BAPI handler
itself. Shims are not needed in this case.
This seems like an ideal solution, but I'm unable to find the
VBAPI.386 handler in Microsoft's WFWT32.EXE archive. It does
exist in the older WFWTCP.EXE archive, but that version does
not support the 32-bit protected mode tcp stack that we want
to run. The notes with the WFWT32 archive indicate that it
is a complete refresh of WFWTCP. Did Microsoft drop support
of BAPI?